Modular paging device

ABSTRACT

Example embodiments involve modular paging device to pass incoming messages off, through Wi-Fi or cellular data, to a central server. This central server handles a response request, and sends the message to a corresponding pager address found within a pager network, allowing a closed loop two-way communication handled through a graphical user interface which may be displayed at the client device.

CLAIM OF PRIORITY

This application is a continuation-in-part application of and claimspriority benefit from U.S. patent application Ser. No. 15/877,986, filedon Jan. 23, 2018 and entitled “ENHANCED PAGER NETWORK,” and which ishereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present invention relates to a portable electronic device forstorage and transfer of digital data.

BACKGROUND

Current paging technology is cumbersome and out of date, forcingrestrictions with accessibility and utility on its users. Pagersgenerally include receiving circuitry to receive a signal from a remotetransmitting station and respond with an audio or visual notificationsto notify a user of the page. To satisfy the paging function, pagersdiffer from telephone equipment in that pagers do not includetransmission capabilities, but only receiver capabilities. Pagers do notsupport real time, two-way communication.

Presently, a majority of hospitals utilize pagers as a means ofcommunication between healthcare providers due to the low cost, batterylife, and robust network architecture. Despite these benefits, pagersstill come with significant drawbacks and limitations as a result of thelimited of two-way communication, and limited display capabilities.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIG. 1 is a network diagram depicting a client-server system, withinwhich one example embodiment may be deployed.

FIG. 2 is a block diagram illustrating components of a paging system,according to some example embodiments.

FIG. 3 is a flowchart illustrating operations of the paging system inforwarding message data to a client device, according to some exampleembodiments.

FIG. 4 is a flowchart illustrating operations of the paging system inforwarding message data to a client device, according to some exampleembodiments.

FIG. 5 is a flowchart illustrating operations of the paging system indelivering a response to message data, according to some exampleembodiments.

FIG. 6 is a diagram illustrating various functional components of apager module, according to some example embodiments.

FIG. 7 is a diagram illustrating various embodiments of a pager module.

FIG. 8 is an interaction diagram illustrating a flow of data, accordingto some example embodiments.

FIG. 9 is an interface diagram illustrating a graphical user interfacepresented at a client device, according to certain example embodiments.

FIG. 10 is an interface diagram illustrating a graphical user interfacepresented at a client device, according to certain example embodiments.

FIG. 11 is an interface diagram illustrating a graphical user interfacepresented at a client device, according to certain example embodiments.

FIG. 12 is an interface diagram illustrating a graphical user interfacepresented at a client device, according to certain example embodiments.

FIG. 13 is a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein.

DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments forcarrying out the inventive subject matter. Embodiments may be practicedwithout some or all of these details. It will be understood that theforgoing disclosure is not intended to limit the scope of the claims tothe described embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe scope of the disclosure as defined by the appended claims. Inaddition, well known features may not have been described in detail toavoid unnecessarily obscuring the subject matter.

As discussed above, current paging technology is cumbersome and out ofdate, forcing restrictions with accessibility and utility on its users.The proposed invention discloses example embodiments that comprise aspecially configured pager module, modified with the addition of a lowenergy connectivity module (e.g., Bluetooth LE module (5.0)), and aimsto tackle the inherent limitations of existing pagers by facilitating alink with current generation client devices such as smartphones, withoutnecessitating any need for modifications upon existing, and alreadyrobust, pager network functionality.

In some example embodiments, a client device passes incoming messagesoff, through wi-fi or cellular data, to a central server. This centralserver handles a response request, and sends the message to acorresponding pager address found within a pager network, allowing aclosed loop two-way communication handled through a graphical userinterface which may be displayed at the client device. Such embodimentsfacilitate rapid communication through an existing pager network, whilealso allowing for a seamless fallback to the original pager system inthe case of cellular/wi-fi network outages, such that messages remainaccessible through the link between the client device and the pagermodule.

As a second benefit, such embodiments enable rich multi-mediacommunication within an existing pager network. As each pager module maybe associated with a specific address or device identifier (e.g., acapcode), which would be used to identify individuals or services tiedto a specific client device. For instance, a client device may be set toreceive a common capcode for emergency services, as well as the capcodespecific to the user. This allows for both announcements and targetedinformation to be received by the client device. With each userspecified by a unique capcode, these codes can be used as specificidentifiers for a central server to communicate multi-media informationback and forth between users on a network. This has many benefits: auser can make direct phone calls using information sent through thesystem, request VoIP, video over IP, recorded images, recorded messages,recorded video, or file transfer, without exposing a personal phonenumber. As this network may be connected to the internet, communicationsto existing services outside of the augmented pager network would alsobe possible while keeping the user's privacy tied to their uniquenetwork identifier.

Another benefit comes inherently from the improvements found in BTLE5.0. Pairing and communications are extremely low energy, and do not taxthe battery of the pager module itself. Introduced in BTLE 5.0 alsoexists the ability for extremely quick pairing to multiple devices. Inthis way, the multiple pager modules may be paired with a single device,or multiple devices may be paired to a single pager module. In someexample embodiments, an application executing at the client device isconfigured to accept and parse the incoming messages for the user. Inaddition to this, the extended range of BTLE 5.0 allows for interestingpossibilities, such as an intra-network of BT enabled pager module tocommunicate with client devices surrounding them (e.g., within ageo-fenced area). This could allow for emergency services tointelligently target users based off proximity and activity. Couplingthis information with location services found on the client device, theserver or other could use this information to assess current personnelavailability.

According to certain example embodiments, a pager system transmitsmessage data to a pager module based on attributes of the message dataincluding an identifier of the pager module. The pager module identifiesa client device in response to receiving the message data, and forwardsthe message data to the client device. The client device causes displayof a notification in response to receiving the message data. In someexample embodiments, the message data comprises message content whichmay include text, image, video, as well as location data identifying alocation, and useable by a client device to navigate a user to adestination.

In some example embodiments, a pager module may be paired or otherwiseassociated with one or more client devices within a database. Messagesreceived at the pager module may thereby be forwarded by variouscommunication means (e.g., Bluetooth) to the one or more paired clientdevices. In further embodiments, the client device may respond to themessages forwarded by the pager module, and in response a central pagersystem may route and distribute the responses to the messages torecipient devices.

FIG. 1 is an example embodiment of a high-level client-server-basednetwork architecture 100. A networked system 102, in the example form ofa pager network, provides server-side functionality via a network 104(e.g., the Internet or wide area network (WAN), Bluetooth) to one ormore client devices 110. FIG. 1 illustrates, for example, a web client112 (e.g., a browser, such as the Internet Explorer® browser developedby Microsoft® Corporation of Redmond, Wash. State), clientapplication(s) 114, and an enhanced paging application 116 executing onthe client device 110.

The client device 110 may comprise, but is not limited to, a wearabledevice, mobile phone, desktop computer, laptop, portable digitalassistant (PDA), smart phone, tablet, ultra-book, netbook, laptop,multi-processor system, microprocessor-based or programmable consumerelectronics, game console, set-top box, or any other communicationdevice that a user may utilize to access the networked system 102. Insome embodiments, the client device 110 comprises a display module (notshown) to display information (e.g., in the form of user interfaces). Infurther embodiments, the client device 110 comprises one or more oftouch screens, accelerometers, gyroscopes, cameras, microphones, globalpositioning system (GPS) devices, and so forth. The client device 110may be a device of a user configured to facilitate communication withinthe networked system 102. One or more portions of the network 104 may bean ad hoc network, an intranet, an extranet, a virtual private network(VPN), a local area network (LAN), a wireless LAN (WLAN), a wide areanetwork (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN),a portion of the Internet, a portion of the public switched telephonenetwork (PSTN), a cellular telephone network, a wireless network, a WiFinetwork, a WiMax network, a Wireless Mesh Network (WMN), or acombination of two or more such networks.

The client device 110 may include one or more client applications 114(also referred to as “apps”) such as, but not limited to, a web browser,messaging application, electronic mail (email) application, a navigationapplication, and the like. In some embodiments, the clientapplication(s) 114 is configured to locally provide the user interfaceand at least some of the functionalities with the client application(s)114 configured to communicate with the networked system 102, on an asneeded basis, for data or processing capabilities not locally available(e.g., access to a database of items available for sale, to authenticatea user, to verify a method of payment). Conversely, the client device110 may use its web browser to access data hosted on the networkedsystem 102 to generate and provide various user interfaces.

One or more users 106 may be a person, a machine, or other means ofinteracting with the client device 110. In example embodiments, the user106 is not part of the network architecture 100, but may interact withthe network architecture 100 via the client device 110 or other means.For instance, the user 106 provides input (e.g., touch screen input,alphanumeric input, text-to-speech, or speech-to-text) to the clientdevice 110 and the input is communicated to the networked system 102 viathe network 104. In this instance, the networked system 102, in responseto receiving the input from the user 106, communicates information tothe client device 110 via the network 104 to be presented to the user106. In this way, the user 106 can interact with the networked system102 using the client device 110.

An application program interface (API) server 120 and a web server 122are coupled to, and provide programmatic and web interfaces respectivelyto, one or more application servers 140. The application server(s) 140may host a paging system 150, which provides functionality operable toprovide a means for managing links between one or more client device(e.g., client device 110), and a pager module 130, enabling a singledevice (e.g., the client device 110) to be utilized for bothauthentication and paging. For example, the paging system 150distributes message data across the network 102 to a pager module 130.The pager module 130 identifies the client device 110 based on factorsincluding attributes of the message data, and associations of pageridentifiers and device identifiers located within the database(s) 126,and forwards the message data to the identified client device (e.g.,client device 110). The enhanced paging application 116 causes displayof a notification in response to receiving the message data at theclient device 110.

Further, while the client-server-based network architecture 100 shown inFIG. 1 employs a client-server architecture, the present inventivesubject matter is of course not limited to such an architecture, andcould equally well find application in a distributed, or peer-to-peer,architecture system, for example. The paging system 150 could also beimplemented as standalone software programs, which do not necessarilyhave networking capabilities.

The web client 112 may access the various publication and paymentsystems 142 and 144 via the web interface supported by the web server122. Similarly, the enhanced paging application 116 accesses the variousservices and functions provided by the paging system 150 via theprogrammatic interface provided by the API server 120. The enhancedpaging application 116 may, for example, generate and cause display ofnotifications in response to receiving message data from an associatedpager module 130.

FIG. 2 is a block diagram illustrating components of the paging system150 that configure the paging system 150 to distribute message data to apager module 130, forward the message data from the pager module 130 toa client device 110, and cause display of a notification at the clientdevice 110 in response to receiving the message data, according to someexample embodiments. The paging system 150 is shown as including areceiver module 202, an identification module 204, a communicationmodule 206, and a notification module 208, all configured to communicatewith each other (e.g., via a bus, shared memory, or a switch). Any oneor more of these modules 202-208 may be implemented using one or moreprocessors 210 (e.g., by configuring such one or more processors 210 toperform functions described for that module) and hence may include oneor more of the processors 210.

Any one or more of the modules 202-208 described may be implementedusing hardware alone (e.g., one or more of the processors 210 of amachine) or a combination of hardware and software. For example, anymodule described of the paging system 150 may physically include anarrangement of one or more of the processors 210 (e.g., a subset of oramong the one or more processors of the machine) configured to performthe operations described herein for that module. As another example, anymodule of the paging system 150 may include software, hardware, or both,that configure an arrangement of one or more processors 210 (e.g., amongthe one or more processors of the machine) to perform the operationsdescribed herein for that module. Accordingly, different modules of thepaging system 150 may include and configure different arrangements ofsuch processors 210 or a single arrangement of such processors 210 atdifferent points in time. Moreover, any two or more modules of thepaging system 150 may be combined into a single module, and thefunctions described herein for a single module may be subdivided amongmultiple modules. Furthermore, according to various example embodiments,modules described herein as being implemented within a single machine,database, or device may be distributed across multiple machines,databases, or devices.

FIG. 3 is a flowchart illustrating operations of the paging system 150in performing a method 300 of forwarding message data from a pagermodule 130 to a client device 110, according to some exampleembodiments.

In operation 302, the paging system 150 transmits message data receivedfrom a first client device to the pager module 130. The first clientdevice may include the database server 124, as well as a third partydevice executed by a third party. The message data comprises at leastmessage content, a device identifier, a user identifier, and a pageridentifier. For example, a user may generate and send a page from acentral system associated with the database server 124, wherein the pageincludes an identification of a specific pager, individual, or groupidentifier for a group of individuals.

In some embodiments, the paging system 150 may further comprise aprotocol converter to convert between messaging protocols. For example,message data received from the first client device may be in a firstprotocol not supported by the pager module 130. In response to receivingthe message data from the first client device, the protocol converterconverts the message data into a protocol suitable for the pager module130.

In operation 304, a receiver module 202 associated with the pager module130 receives the message data through the network 104. In someembodiments the network 104 may include a Simple Network Paging Protocol(SNPP), a Telelocator Alphanumeric Protocol (TAP), FLEX, ReFLEX, PostOffice Code Standardisation Advisory Group (POCSAG), GOLAY, EnhancedRadio Messaging System (ERMS), and NTT.

In operation 306, an identification module 204 identifies a secondclient device (e.g., the client device 110) to forward the message data,and provides the pager module 130 with an address of the identifiedclient device. In some example embodiments, the pager module 130 may bepaired or otherwise linked to the client device 110 via a wireless meansincluding Bluetooth and Personal Area Networks (PANs). In furtherembodiments, a pager identifier associated with the pager module 130 maybe linked with a device identifier or user identifier associated withthe client device 110 within the database(s) 126.

In operation 308, a communication module 206 associated with the pagermodule 130 forwards the message data to the second client device (e.g.,client device 110). In some example embodiments, the pager module 130may communicate with the client device 110 via Bluetooth, or a PAN. Inresponse to receiving the message data, at operation 310 a notificationmodule 208 associated with the client device 110 generates and causesdisplay of a notification that includes a presentation of the messagedata within a graphical user interface displayed at the client device110. For example, the presentation may include a display of messagecontent of the message data, as well as an indication of a sender of themessage data.

FIG. 4 is a flowchart illustrating operations of the paging system 150in performing a method 400 of forwarding message data from a pagermodule 130 to a client device 110, according to some exampleembodiments. As shown in FIG. 4, one or more operations 402, and 404 maybe performed as part (e.g., a precursor task, a subroutine, or aportion) of the method 300, according to some example embodiments.

In operation 402, the paging system 150 associated a pager identifier ofthe pager module 130 to one or more user identifiers or deviceidentifiers associated with at least the client device 110 within thedatabase(s) 126. For example, an administrator of the paging system 150may provide inputs to specify a link between the pager module 130 andthe client device 110. In further embodiments, in response to detectinga pairing of the pager module 130 to the client device 110, the pagingsystem 150 updates the database(s) 126 to reflect the connection of thedevices.

In operation 404, in response to receiving the message data at the pagermodule 130 at operation 304 of the method 300, the paging system 150and/or the pager module 130 identifies the client device 110 from amongone or more client devices, based on the information within thedatabase(s) 126. In some example embodiments, the message data mayinclude a device identifier or user identifier that identifies theclient device 110.

FIG. 5 is a flowchart illustrating operations of the paging system 150in performing a method 500 of delivering a response to the message data,according to some example embodiments. As shown in FIG. 5, one or moreoperations 502, 504, and 506 may be performed as part (e.g., a precursortask, a subroutine, or a portion) of the method 300, according to someexample embodiments.

In operation 502, the communication module 206 of the paging system 150receives a response to the message data from the second client device(e.g., client device 110). The response to the message data may includemessage attributes that include a tag that identifies the message data,a pager identifier that identifies the pager module 130, and a deviceidentifier that identifies the client device 110.

In operation 504, the paging system determines a destination for theresponse based on the message attributes, and at operation 506, thepaging system 150 delivers the response to the destination (e.g., thefirst client device), via the network 104.

FIG. 6 is a diagram 600 illustrating various functional components of apager module 130. As seen in the diagram 600, the pager module 130 maycomprise a demodulator 602, a transmitter 604, an antenna 606, aninductive charging coil 608, and a battery 610, all enclosed within anenclosure 612.

In some example embodiments, the demodulator 602 includes a FrequencyShift Keying (FSK) Demodulator, configured to transmit digitalinformation (e.g., message data) through discrete frequency changes of acarrier signal.

In some example embodiments, the transmitter 604 includes a short waveradio frequency transmitter (e.g., Bluetooth), configured to forwardmessage data between the pager module 130 and a paired client device110.

In some example embodiments the antenna 606 includes a loop antennaconsisting of a loop of wire, and fully enclosed by the enclosure 612.In some example embodiments, the antenna 606 is integrated into aportion of the enclosure 612. For example, the enclosure 612 maycomprise multiple components that come together to form the enclosure612. In some embodiments, the antenna 606 may be molded or formed intoone or more of the components of the enclosure 612.

In some example embodiments, the antenna 606 may be formed into a framethat encompasses a perimeter of a surface of the enclosure 612.

In some example embodiments, the charging coil 608 includes one or moreexposed charging leads to enable a use to plug the pager module 130 intoan outlet (e.g., USB).

In some example embodiments, the enclosure 612 is the form of aproximity card, such as a contactless smart card.

FIG. 7 is a diagram illustrating various embodiments of a pager module130. As seen in FIG. 7, the enclosure 612 of the pager module 130 mayinclude a number of different forms. In some example embodiments, thepager module 130 itself may comprise a modular unit which may beinserted within a number of distinct enclosures (e.g., the enclosure 612of FIG. 6).

In some example embodiments, the enclosure 612 that houses the pagermodule 130 (as seen in FIG. 6) may include the tethered enclosure 702,wherein the tethered enclosure 702 may be communicatively coupled to theclient device 110 via a cable. In some embodiments, the tetheredenclosure 702 may include an extended battery unit to provide power toboth the client device 110, as well as the pager module 130.

For example, the tethered enclosure 702 may comprise a metallic, ornon-metallic housing that includes a connection port to receive a cable,such as a Universal Serial Bus Type-A (USB A) cable, USB Type-B,Mini-USB, Micro-USB, and USB Type-C. A user 106 of a client device 110may connect the pager module 130 to the client device 110 via thetethered enclosure 702, through the integrated connection port.

In some example embodiments, the enclosure 612 that houses the pagermodule 130 (as seen in FIG. 6) may include a key-fob 704. The key-fob704 may comprise a hook or loop to detachably receive a key-ring.

In some example embodiments, the enclosure 612 that houses the pagermodule 130 (as seen in FIG. 6) may include a cell-phone case 706,wherein the client device 110 may be inserted into the cell-phone case706. In further embodiments, the cell-phone case 706 may include anintegrated extended battery that supplies battery power to both thepager module 130 as well as the client device 110.

The cell-phone case 706 may comprise a semi-flexible housing to enclosea device, such as the client device 110, wherein the semi-flexiblehousing encases the client device 110, while exposing a screen of theclient device 110.

In some example embodiments, the enclosure 612 that houses the pagermodule 130 (as seen in FIG. 6) may include a bi-fold case 708, whereinthe client device 110 may be inserted into the bi-fold case 708. Thebi-fold case 708 may comprise a housing to encase the client device 110,as well as a flap to cover a screen of the client device 110.

In some example embodiments, the enclosure 612 that houses the pagermodule 130 (as seen in FIG. 6) may include a band 710 (e.g., awrist-band, an arm-band), wherein the band 710 may be worn by a user106. The band 710 may comprise a fastener, such as a Velcro strap, anelastic band, buckle, tang buckle, deployment clasp, or pushbuttondeployment clasp.

FIG. 8 is an interaction diagram 800 illustrating a flow of data, andvarious interactions between the paging system 150, the pager module130, and a client device 110, according to some example embodiments.

At operation 802, a first user of the paging system 150 generates amessage to be distributed to a second user. The message may for examplecomprise message data (e.g., text data, multi-media content, audiodata), as well as a recipient address (e.g., a pager address), and anidentification of the paging system 150 (e.g., a device identifier,sender address, location data that identifies a location of the pagingsystem 150). At operation 804, the paging system 150 transmits a signalthat includes the message to the pager module 130, wherein the pagermodule 130 is identified by the pager address of the message. In someembodiments the signal is transmitted to the pager module 130 via anetwork, such as the network 104.

At operation 806, the pager module 130 receives the signal from thepaging system 150. For example, the pager module 130 may receive thesignal via the antenna 606, as depicted in FIG. 6. At operation 808, thedemodulator 802 of the pager module 130, demodulates the signal receivedfrom the paging system 150, at the pager module 130. At operation 810,the demodulated signal is transmitted to a client device associated withthe pager module 130 (e.g., client device 110). For example, thedemodulated signal is transmitted to the client device 110 from thepager module 130 via a wireless communication medium, such as Wi-Fi,Bluetooth, or RF.

At operation 812, the client device 110 authenticates the signal basedon the pager address indicated within the message. At operation 814, theclient device 110 causes display of the message within a graphical userinterface, in response to the authentication.

In some embodiments, at operation 814, the client device 110 generatesand transmits a read-receipt to the paging system 150, in response tocausing display of the message. The read receipt may for example includea message identifier that identifies the message, the pager identifierassociated with the client device 110, location data that identifies alocation of the client device 110 at a time of receiving the message,and a time stamp that indicates a time in which the message wasdisplayed at the client device. At operation 816, the paging system 150receives the read receipt from the client device, and authenticates theread receipt based on attributes of the message. For example, the pagingsystem 150 may authenticate the read receipt based on the messageidentifier, the pager identifier, or the location data.

In some embodiments, in response to verifying the message at the pagingsystem 150, the paging system 150 may cause display of an indicationthat the message was received at the client device 110.

FIG. 9 is an interface diagram 900 illustrating a graphical userinterface 905 displayed at a client device 110, according to certainexample embodiments including embodiments described above, as in themethod 300 and the interaction diagram 800.

As seen in the interface diagram 900, the graphical user interface 905may include an interface to associate a pager module 130 with a clientdevice 110. For example, the pager module 130 may be connected (i.e.,paired, linked) with the client device 110 (e.g., through a wiredconnection or using Bluetooth). In response to detecting the connectionbetween the pager module 130 and the client device 110, the notificationmodule 208 may generate and cause display of the status indicator 915.The status indicator 915 may for example indicate that the pager module130 is: connected, not connected, or intermittent.

To authenticate the connection between the client device 110 and thepager module 130, a user 106 may provide authentication credentials intoan authentication menu 920. In some embodiments the authenticationcredentials may include a username and login.

In some example embodiments, the graphical user interface 905 may beconfigured to display a logo 910. The logo 910 may for example be presetby an administrator of the network 104, or may in further embodiments bebased on a logo identifier received from the pager module 130.

For example, the pager module 130 may store a logo identifier thatcomprises display instructions, or a logo identifier that identifies thelogo 910. In response to detecting a connection between the pager module130 and the client device 110, the client device 110 may retrieve thelogo identifier from the pager module 130, and retrieve or otherwiseaccess the logo 910 from a logo repository. For example, the logorepository may be accessible through the web client 112, executed at theclient device 110, may be located within a memory of the client device110, or may be hosted within the database 126, and accessed through theapplication servers 140.

The pager module 130 may therefore be configured to display one or morelogos based on configuration instructions that define a logo, such asthe logo 910. For example, an administrator may configure the pagermodule 130 to display a particular logo.

FIG. 10 is an interface diagram 1000 illustrating a graphical userinterface 1005 displayed at a client device 110, according to certainexample embodiments including embodiments described above, as in themethod 300 and the interaction diagram 800.

As seen in the interface diagram 1000, the graphical user interface 1005may include a messaging interface configured to display messages (suchas the message 1010) received at the pager module 130. The messaginginterface may display a user identifier 1015 associated with a sender ofa message, such as the message 1010. For example, the pager module 130may receive a message that comprises message content and an identifierof a sender of the message. The client device 110 may receive themessage from the pager module 130, parse the message to identify thesender of the message and the message content, and cause display of themessage 1010 within the graphical user interface 1005 along with theuser identifier 1015.

In some embodiments, the graphical user interface 1005 may displaynotifications such as the notification 1020. For example, thenotification 1020 may be distributed to a group of devices associatedwith a message category (e.g., emergency department). For example, auser identifier or device identifier that corresponds with the user 106may be associated with a message category, wherein the message categoryhas a unique messaging address. In response to the user identifier ordevice identifier being associated with the message category, thecommunication module 206 may associate the pager module 130 with theunique messaging address of the message category, and the notificationmodule 208 may display the group identifier 1030 within the graphicaluser interface 1005. A sender may thereby distribute a message ornotification to the message category, and in response, a plurality ofclient devices associated with the message category may be notifiedsimultaneously, for example by the notification 1020.

The user 106 may provide inputs into the graphical user interface 1005using the input menu 1025. In some embodiments, the input menu 1025 maycomprise a keyboard that includes set of alphanumeric icons. In someembodiments, the user 106 may toggle between different input menus. Forexample, the input menu 1025 may additionally include an input field inwhich a user may provide tactile input directly into the graphical userinterface 1005, to draw an input which may then be distributed to one ormore devices.

FIG. 11 is an interface diagram 1100 illustrating a graphical userinterface 1105 displayed at a client device 110, according to certainexample embodiments including embodiments described above, as in themethod 300 and the interaction diagram 800.

As seen in the interface diagram 1100, the graphical user interface 1105may include a group messaging interface to display messages received atone or more distinct message categories (e.g., hospital announcements,emergency department, etc.). For example a user identifier or deviceidentifier that corresponds with the user 106 may be associated with aplurality of message categories, wherein each message category has aunique messaging address. In response to the user identifier or deviceidentifier being associated with the plurality of message categories,the communication module 206 may associate the pager module 130 with theunique messaging address of each message category, and the notificationmodule 208 may display the group identifiers that correspond with themessage categories within the graphical user interface 1105.

In some embodiments, the group identifiers displayed within thegraphical user interface 1105 may include group attributes. For example,the group identifier 1110 includes a display of an identifier of thegroup identifier (e.g., EMERGENCY DEPARTMENT), a display of a number ofusers 1120 associated with the group identified by the group identifier1110, and a display of a number of messages 1115 received at themessaging address of the group identified by the group identifier 1110.

A user 106 may select and display messages associated with a groupwithin an interface, such as within the interface 1005.

FIG. 12 is an interface diagram 1200 illustrating a graphical userinterface 1205 displayed at a client device 110, according to certainexample embodiments including embodiments described above, as in themethod 300 and the interaction diagram 800.

As seen in the interface diagram 1200, the graphical user interface 1205may include a car management interface to enable a user (e.g., the user106) to configure notification settings for messages received at thepager module 130. For example, the graphical user interface 1205includes a display of notification setting 1210 that include an alerttone, a vibrate pattern, as well as whether or not to emit an audiblealert.

The graphical user interface 1205 may also include a presentation of abattery life indicator 1210 that comprises a display of a battery lifeof the pager module 130. For example, the client device 110 may retrievea battery life value from the pager module 130 at time intervals thatmay be defined by the user 106, or may be predefined. In someembodiments, the pager module 130 may send a battery life value to theclient device 110 automatically and based on the intervals, while infurther embodiments the client device 110 may request a battery lifevalue in response to detecting the user 106 requesting a display of thegraphical user interface 1205.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module istangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation, and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., Application Program Interfaces (APIs).)

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor,a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry,e.g., a field programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that that both hardware and software architectures meritconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1300 in the example form of a computer system, within which instructions1316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein may be executed.Additionally, or alternatively, the instructions may implement themodules of FIG. 2. The instructions transform the general,non-programmed machine into a specially configured machine programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1300 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1300 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment.

The machine 1300 may comprise, but not be limited to, a server computer,a client computer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a set-top box (STB), a personal digital assistant(PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smart watch), a smarthome device (e.g., a smart appliance), other smart devices, a webappliance, a network router, a network switch, a network bridge, or anymachine capable of executing the instructions 1316, sequentially orotherwise, that specify actions to be taken by machine 1300. Further,while only a single machine 1300 is illustrated, the term “machine”shall also be taken to include a collection of machines 1300 thatindividually or jointly execute the instructions 1316 to perform any oneor more of the methodologies discussed herein.

The machine 1300 includes processors 1310, memory 1330, and I/Ocomponents 1350, which may be configured to communicate with each othersuch as via a bus 1302. In an example embodiment, the processors 1310(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CISC)processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, processor 1312and processor 1314 that may execute instructions 1316. The term“processor” is intended to include multi-core processor that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.13 shows multiple processors, the machine 1300 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core process), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory/storage 1330 may include a memory 1332, such as a mainmemory, or other memory storage, and a storage unit 1336, bothaccessible to the processors 1310 such as via the bus 1302. The storageunit 1336 and memory 1332 store the instructions 1316 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1316 may also reside, completely or partially, within thememory 1332, within the storage unit 1336, within at least one of theprocessors 1310 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1300. Accordingly, the memory 1332, the storage unit 1336, and thememory of processors 1310 are examples of machine-readable media.

As used herein, “machine-readable medium” means a device able to storeinstructions and data temporarily or permanently and may include, but isnot be limited to, random-access memory (RAM), read-only memory (ROM),buffer memory, flash memory, optical media, magnetic media, cachememory, other types of storage (e.g., Erasable Programmable Read-OnlyMemory (EEPROM)) and/or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 1316. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 1316) for execution by a machine (e.g., machine1300), such that the instructions, when executed by one or moreprocessors of the machine 1300 (e.g., processors 1310), cause themachine 1300 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes transitory signals per se.

The I/O components 1350 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1350 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components1350 may include many other components that are not shown in FIG. 13.The I/O components 1350 are grouped according to functionality merelyfor simplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 1350 mayinclude output components 1352 and input components 1354. The outputcomponents 1352 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display,organic light-emitting diode (OLED), a liquid crystal display (LCD), aprojector, or a cathode ray tube (CRT)), electronic paper (e-paper),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1354 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1350 may includebiometric components 1356, motion components 1358, environmentalcomponents 1360, or position components 1362 among a wide array of othercomponents. For example, the biometric components 1356 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1358 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1360 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1362 mayinclude location sensor components (e.g., a Global Position System (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1350 may include communication components 1364operable to couple the machine 1300 to a network 1380 or devices 1370via coupling 1382 and coupling 1372 respectively. For example, thecommunication components 1364 may include a network interface componentor other suitable device to interface with the network 1380. In furtherexamples, communication components 1364 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1370 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1364 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1364 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1364, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

Transmission Medium

In various example embodiments, one or more portions of the network 1380may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, the network 1380 or a portion of the network 1380may include a wireless or cellular network and the coupling 1382 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 1382 may implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 1316 may be transmitted or received over the network1380 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components1364) and utilizing any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1316 may be transmitted or received using a transmission medium via thecoupling 1372 (e.g., a peer-to-peer coupling) to devices 1370. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying instructions 1316 forexecution by the machine 1300, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the inventive subject matter may be referred to herein, individuallyor collectively, by the term “invention” merely for convenience andwithout intending to voluntarily limit the scope of this application toany single disclosure or inventive concept if more than one is, in fact,disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A system comprising: one or more processors; anda memory storing instructions that, when executed by at least oneprocessor among the one or more processors, cause the system to performoperations comprising: receiving message data at a pager module, themessage data comprising at least a sender identifier that identifies asource of the message data; forwarding the message data from the pagermodule to a client device in response to the receiving the message dataat the pager module; identifying the source of the message data at theclient device based on the sender identifier; and causing display of anotification at the client device, the notification based on the sourceof the message data.
 2. The system of claim 1, wherein the instructionscause the system to perform operations further comprising: causing aconnection between the pager module and the client device via aBluetooth module; detecting the connection between the pager module andthe client device; retrieving display instructions from the pager moduleat the client device in response to the detecting the connection; andcausing display of a graphical user interface that includes a logo atthe client device, the logo based on the display instructions.
 3. Thesystem of claim 2, wherein the instructions cause the system to performoperations further comprising: causing display of a connection status atthe client device in response to the detecting the connection betweenthe pager module and the client device.
 4. The system of claim 1,wherein the message data is first message data, and the instructionscause the system to perform operations further comprising: associatingan identifier that corresponds with the client device to a groupidentifier; receiving second message data addressed to the groupidentifier at the pager module; forwarding the second message data tothe client device based on the associating the identifier thatcorresponds with the client device to the group identifier; and causingdisplay of the second message data within a group message interface thatcorresponds with the group identifier.
 5. The system of claim 1, whereinthe instructions cause the system to perform operations furthercomprising: retrieving a battery life value from the pager module; andcausing display of a presentation of the battery life value at theclient device.
 6. The system of claim 5, wherein the retrieving thebattery life value from the pager module includes: receiving a requestto cause display of the presentation of the battery life value at theclient device; and retrieving the battery life value from the pagermodule in response to the request to cause display of the presentationof the battery life value.
 7. The system of claim 1, wherein the pagermodule comprises a device enclosure, the device enclosure including acell-phone case.
 8. A method comprising: receiving message data at apager module, the message data comprising at least a sender identifierthat identifies a source of the message data; forwarding the messagedata from the pager module to a client device in response to thereceiving the message data at the pager module; identifying the sourceof the message data at the client device based on the sender identifier;and causing display of a notification at the client device, thenotification based on the source of the message data.
 9. The method ofclaim 8, wherein the method further comprises: causing a connectionbetween the pager module and the client device via a Bluetooth module;detecting the connection between the pager module and the client device;retrieving display instructions from the pager module at the clientdevice in response to the detecting the connection; and causing displayof a graphical user interface that includes a logo at the client device,the logo based on the display instructions.
 10. The method of claim 8,wherein the method further comprises: causing display of a connectionstatus at the client device in response to the detecting the connectionbetween the pager module and the client device.
 11. The method of claim8, wherein the message data is first message data, and the methodfurther comprises: associating an identifier that corresponds with theclient device to a group identifier; receiving second message dataaddressed to the group identifier at the pager module; forwarding thesecond message data to the client device based on the associating theidentifier that corresponds with the client device to the groupidentifier; and causing display of the second message data within agroup message interface that corresponds with the group identifier. 12.The method of claim 8, wherein the method further comprises: retrievinga battery life value from the pager module; and causing display of apresentation of the battery life value at the client device.
 13. Themethod of claim 12, wherein the retrieving the battery life value fromthe pager module includes: receiving a request to cause display of thepresentation of the battery life value at the client device; andretrieving the battery life value from the pager module in response tothe request to cause display of the presentation of the battery lifevalue.
 14. The method of claim 8, wherein the pager module comprises adevice enclosure, the device enclosure including a cell-phone case. 15.A non-transitory machine-readable storage medium comprising instructionsthat, when executed by one or more processors of a machine, cause themachine to perform operations comprising: receiving message data at apager module, the message data comprising at least a sender identifierthat identifies a source of the message data; forwarding the messagedata from the pager module to a client device in response to thereceiving the message data at the pager module; identifying the sourceof the message data at the client device based on the sender identifier;and causing display of a notification at the client device, thenotification based on the source of the message data.
 16. Thenon-transitory machine-readable storage medium of claim 15, wherein theinstructions cause the machine to perform operations further comprising:causing a connection between the pager module and the client device viaa Bluetooth module; detecting the connection between the pager moduleand the client device; retrieving display instructions from the pagermodule at the client device in response to the detecting the connection;and causing display of a graphical user interface that includes a logoat the client device, the logo based on the display instructions. 17.The non-transitory machine-readable storage medium of claim 15, whereinthe instructions cause the machine to perform operations furthercomprising: causing display of a connection status at the client devicein response to the detecting the connection between the pager module andthe client device.
 18. The non-transitory machine-readable storagemedium of claim 15, wherein the message data is first message data, andthe instructions cause the machine to perform operations furthercomprising: associating an identifier that corresponds with the clientdevice to a group identifier; receiving second message data addressed tothe group identifier at the pager module; forwarding the second messagedata to the client device based on the associating the identifier thatcorresponds with the client device to the group identifier; and causingdisplay of the second message data within a group message interface thatcorresponds with the group identifier.
 19. The non-transitorymachine-readable storage medium of claim 15, wherein the instructionscause the machine to perform operations further comprising: retrieving abattery life value from the pager module; and causing display of apresentation of the battery life value at the client device.
 20. Thenon-transitory machine-readable storage medium of claim 19, wherein theretrieving the battery life value from the pager module includes:receiving a request to cause display of the presentation of the batterylife value at the client device; and retrieving the battery life valuefrom the pager module in response to the request to cause display of thepresentation of the battery life value.